Dynamically tasking one or more surveillance resources

ABSTRACT

In one embodiment, a system for dynamically tasking one or more surveillance resources includes a first logical layer identifying a collection requirement (CR) and a second logical layer identifying one or more surveillance resources in the CR. Each of the surveillance resources includes one or more sensors. The system also includes a third logical layer specifying how each of the sensors in the surveillance resources in the CR should carry out surveillance.

TECHNICAL FIELD OF THE INVENTION

This invention relates generally to surveillance resources and moreparticularly to dynamically tasking one or more surveillance resources.

BACKGROUND

In current collection systems, tasking one or more surveillanceresources (such as, for example, one or more sensors on one or morespacecraft) to surveil a target typically involves generating one ormore tasks for the surveillance resources, getting a central taskingauthority (CTA) to approve the tasks, and then deploying the tasks tothe surveillance resources. Generating a task for a surveillanceresource often requires specialized expertise, and approval from a CTAoften requires considerable time. As a result, current collectionsystems typically do not enable users to readily task surveillanceresources to surveil targets.

SUMMARY

According to the present invention, disadvantages and problemsassociated with data communication may be reduced or eliminated.

In one embodiment, a system for dynamically tasking one or moresurveillance resources includes a first logical layer identifying acollection requirement (CR) and a second logical layer identifying oneor more surveillance resources in the CR. Each of the surveillanceresources includes one or more sensors. The system also includes a thirdlogical layer specifying how each of the sensors in the surveillanceresources in the CR should carry out surveillance.

Particular embodiments of the present invention may provide one or moretechnical advantages. As an example, particular embodiments reduce timerequirements typically associated with tasking surveillance resources.Particular embodiments simplify instructions used to task surveillanceresources. Particular embodiments lend modularization, standardization,or both to tasking surveillance resources. In particular embodiments,such modularization, standardization, or both enables thin tasking. Inparticular embodiments, users need not have specialized expertise totask surveillance resources. Particular embodiments enable users toreadily task and retask surveillance resources in response to observedevents. Certain embodiments may provide all, some, or none of thesetechnical advantages. Certain embodiments may provide one or more othertechnical advantages, one or more of which may be readily apparent tothose skilled in the art from the figures, descriptions, and claimsherein.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present invention andthe features and advantages thereof, reference is made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates an example system for dynamically tasking one or moresurveillance resources;

FIG. 2 illustrates an example collector system in the system illustratedin FIG. 1; and

FIG. 3 illustrates an example collection requirement (CR) in thecollector system illustrated in FIG. 2;

FIG. 4 illustrates example Intelligence, Surveillance, andReconnaissance Requirements (ISRRs);

FIG. 5 illustrates an example target definition in the CR illustrated inFIG. 3; and

FIG. 6 illustrates an example method for dynamically tasking one or moresurveillance resources.

DESCRIPTION OF EXAMPLE EMBODIMENTS

FIG. 1 illustrates an example system 10 for dynamically tasking one ormore surveillance resources. System 10 includes one or more sensorsystems 12, a collector system 14, one or more users 16, and a CTA 18. Asensor system 12 includes one or more components for surveilling one ormore targets and communicating the surveillance to collector system 14.As an example and not by way of limitation, a sensor system 12 mayinclude one or more spacecraft (such as, for example, one or moreunmanned satellites) including components for surveilling one or moretargets and communicating the surveillance to collector system 14. Asanother example, a sensor system 12 may include one or more aircraft(such as, for example, one or more unmanned aerial vehicles (UAVs))including components for surveilling one or more targets andcommunicating the surveillance to collector system 14. Reference to a“target” encompasses anything surveillable, where appropriate. As anexample and not by way of limitation, a target may include a geographicsite, a building, a facility, equipment, a vehicle, a person, or anothertarget or a combination of two or more such targets. Reference to“surveilling” a target encompasses observing the target, whereappropriate. As an example and not by way of limitation, surveilling atarget may include photographing or otherwise collecting images of thetarget. In particular embodiments, one or more sensor systems 12 areeach a combination of multiple sensor systems 12.

Collector system 14 includes one or more components for communicatingcommands to one or more sensor systems 12. As an example and not by wayof limitation, collector system 14 may communicate one or more commandsto a sensor system 12 causing sensor system 12 to surveil one or moretargets and communicate the surveillance to collector system 14.Collector system 14 may communicate the commands to sensor system 12automatically or in response to input. Collector system 14 also includesone or more components for receiving surveillance from one or moresensor systems 12 and communicating the surveillance to one or moreusers 16. In particular embodiments, collector system 14 directlycommunicates surveillance to one or more users 16, communicatessurveillance to one or more users 16 through one or more intermediateentities that process the surveillance for use, or both. In particularembodiments, collector system 14 communicates with a sensor system 12via one or more wireless communication links (such as, for example, oneor more satellite communication links) between sensor system 12 andcollector system 14.

Collector system 14 also includes one or more components for receivinginstructions from one or more users 16, CTA 18, or both directingcollector system 14 to task one or more surveillance resources, asdescribed below. In particular embodiments, collector system 14communicates with a user 16 via a wireline, optical, wireless, or othercommunication link or a combination of two or more such communicationlinks. In particular embodiments, collector system 14 communicates witha user 16 via an Internet Protocol (IP)-based communication network. Todirect collector system 14 to task one or more surveillance resources, auser 16 communicates a plugin to collector system 14 via one or morecommunication links between collector system 14 and user 16 or via CTA18. In particular embodiments, a plugin from a user 16 includes data,executable code, or both modifying one or more components (such as, forexample, one or more files including data, executable code, or bothstored at collector system 14) of collector system 14, adding one ormore components to collector system 14, or removing one or morecomponents from collector system 14. In particular embodiments,collector system 14 communicates with CTA 18 via a wireline, optical,wireless, or other communication link or a combination of two or moresuch communication links. In particular embodiments, collector system 14communicates with CTA 18 via an IP-based communication network. Todirect collector system 14 to task one or more surveillance resources,CTA 18 communicates an envelope to collector system 14 via one or morecommunication links between collector system 14 and CTA 18. Inparticular embodiments, an envelope from CTA 18 includes data,executable code, or both making one or more surveillance resourcesavailable for surveilling one or more targets. In particularembodiments, CTA 18 generates an envelope and communicates the envelopeto collector system 14 in response to one or more requests from one ormore users 16. In particular embodiments, collector system 14 is acombination of multiple collector systems 14.

A user 16 requests surveillance resources from CTA 18, directs collectorsystem 14 to task surveillance resources, and uses surveillancecommunicated from collector system 14. As an example and not by way oflimitation, a user 16 may include military personnel carrying outorders. The military personnel may request surveillance resources fromCTA 18 and, if CTA 18 approves the request, use the surveillanceresources to surveil one or more targets. The surveillance may help themilitary personnel carry out their orders. In response to one or moreevents, the military personnel may communicate one or more plugins tocollector system 14 directing collector system 14 to task thesurveillance resources according to particular needs of the militarypersonnel. A user 16 includes a person, a computer system acting oninput from one or more persons, a computer system operatingsubstantially independent of input from one or more persons, or anotheruser 16 or a combination of two or more such users 16. As an example andnot by way of limitation, a user 16 may include military personnel,intelligence personnel, or both. As another example, a user 16 mayinclude one or more computer systems acting on input from militarypersonnel, intelligence personnel, or both. As another example, a user16 may include one or more computer systems carrying out one or moretasks related to military operations, intelligence operations, or both,but operating substantially independent of input from military personneland intelligence personnel. In particular embodiments, one or more users16 are each a combination of multiple users 16. CTA 18 has authorityover utilization of surveillance resources. As an example and not by wayof limitation, CTA 18 may have authority over which sensor systems 12surveil which targets for which users 16 at which times. CTA 18 includesa person, a computer system acting on input from one or more persons, acomputer system operating substantially independent of input from one ormore persons, or another CTA 18 or a combination of two or more suchCTAs 18. In particular embodiments, CTA 18 is a combination of multipleCTAs 18.

FIG. 2 illustrates an example collector system 14. Collector system 14includes one or more interfaces 20 for communication with one or moreusers 16, an interface 22 for communication with CTA 18, and one or moreinterfaces 24 for communication with one or more sensor systems 12. Inparticular embodiments, interfaces 20, 22, and 24 are separate from eachother. In particular embodiments, two or more of interfaces 20, 22, and24 share a hardware, software, or embedded logic component or acombination of two or more such components with each other. Inparticular embodiments, two or more of interfaces 20, 22, and 24collectively provide a single interface for communication with two ormore of users 16, CTA 18, and sensor systems 12. Collector system 14also includes one or more collection requirements (CRs) 26 and one ormore target definitions 28. A CR 26 defines one or more surveillanceresources for surveilling one or more targets, as described below. Atarget definition 28 defines one or more targets for surveillance, asdescribed below.

A target-CR link 30 provides a logical link between a CR 26 and a targetdefinition 28 enabling application of surveillance resources defined inCR 26 to targets defined in target definition 28. A CR 26 is logicallylinkable to one or more target definitions 28, and vice versa. Inparticular embodiments, a target-CR link 30 identifies a CR 26 and atarget definition 28 logically linked to each other by target-CR link30. In particular embodiments, target-CR link 30 specifies one or moreattributes of the logical link between CR 26 and target definition 28identified in target-CR link 30. As an example and not by way oflimitation, target-CR link 30 may specify one or more time intervals fortarget-CR link 30. During a specified time interval, target-CR link 30may logically link CR 26 and target definition 28 identified intarget-CR link 30 with each other to enable application of surveillanceresources defined in CR 26 to targets defined in target definition 28.As another example, target-CR link 30 may specify a current status oftarget-CR link 30, such as “on” or “off.” Target-CR link 30 may enableapplication of surveillance resources defined in CR 26 to targetsdefined in target definition 28 when the current status of target-CRlink 30 is “on” and disable application of surveillance resourcesdefined in CR 26 to targets defined in target definition 28 when thecurrent status of target-CR link 30 is “off.” In particular embodiments,one or more Extensible Markup Language (XML) or other files include oneor more target-CR links 30.

In particular embodiments, a user 16, CTA 18, or both generate atarget-CR link 30. As an example and not by way of limitation, a user 16may want one or more targets surveilled. User 16 may generate a requestfor the surveillance and communicate the request to CTA 18, and therequest may identify the targets that user 16 wants surveilled andspecify one or more observations for collection on the identifiedtargets. If CTA 18 approves the request, CTA 18 may generate one or moretarget-CR links 30 providing one or more logical links between a CR 26defining one or more surveillance resources for collecting the specifiedobservations and one or more target definitions 28 defining the one ormore identified targets. CTA 18 may then communicate target-CR links 30to collector system 14. As another example, in response to one or morerecent events, a user 16 may want one or more targets surveilledimmediately. A CR 26 at collector system 14 may define one or moresurveillance resources for surveilling the targets that user 16 wantssurveilled, one or more target definitions 28 at collector system 14 maydefine the targets that user 16 wants surveilled, and user 16 may haveauthorization to task the surveillance resources defined in CR 26 tosurveil the targets defined in target definitions 28. User 16 maygenerate one or more target-CR links 30 providing one or more logicallinks between CR 26 and target definitions 28 and communicate target-CRlinks 30 in a plugin to collector system 14. The plugin may facilitateimmediate surveillance of the targets that user 16 wants surveilled.

FIG. 3 illustrates an example CR 26. In particular embodiments, CR 26defines surveillance resources for one or more intelligence disciplines.As an example and not by way of limitation, CR 26 may definesurveillance resources for Imagery Intelligence (IMINT), SignalsIntelligence (SIGINT), or Human-Source Intelligence (HUMINT) or acombination of two or more such intelligence disciplines. CR 26 includescore 34, one or more status modules 36, and an Intelligence,Surveillance, and Reconnaissance Requirement (ISRR) tag 38. Core 34defines one or more elements of CR 26 that are not readily changeable.In particular embodiments, one or more Extensible Markup Language (XML)or other files include core 34. Core 34 includes a CR identifier 42, astart indicator 44, a stop indicator 46, one or more sensor tags 48, andone or more strategies 50 that each correspond to a sensor tag 48.Although a particular core 34 including particular components isillustrated and described, the present invention contemplates anysuitable core 34 including any suitable components.

CR identifier 42 uniquely identifies CR 26. In particular embodiments,CR identifier 42 is a rule-based identifier. In particular embodiments,CR identifier 42 enables linking between CR 26 and one or more targetdefinitions 28. As an example and not by way of limitation, a target-CRlink 30 between CR 26 and a target definition 28 may specify CRidentifier 42 to logically link target definition 28 to CR 26. Inparticular embodiments, a user 16 specifies CR identifier 42 to accessCR 26. As an example and not by way of limitation, user 16 may address aplugin to CR 26 according to CR identifier 42 so that the plugin reachesCR 26. The plugin may modify CR 26. Start indicator 44 indicates when CR26 becomes operational, and stop indicator 46 indicates when CR 26becomes nonoperational. As an example and not by way of limitation, ifstart indicator 44 indicated that CR 26 became operational at midnight,1 Jan. 2005, and stop indicator 44 indicated that CR 26 becamenonoperational at midnight, 1 Feb. 2005, surveillance resources definedin CR 26 would be available for surveilling targets between midnight, 1Jan. 2005, and midnight, 1 Feb. 2005.

Sensor tags 48 each identify one or more sensors in one or more sensorsystems 12 for surveilling one or more targets. As an example and not byway of limitation, a first sensor tag 48 in core 34 may identify a firstsensor in a first sensor system 12 and a second sensor tag 48 in core 34may identify a second sensor in a second sensor system 12. When CR 26 isoperational, collector system 14 may cause the first sensor to surveilone or more targets and first sensor system 12 to communicate thesurveillance to collector system 14, cause the second sensor to surveilone or more targets and second sensor system 12 to communicate thesurveillance to collector system 14, or both. A strategy 50corresponding to a sensor tag 48 identifying a sensor indicates how thesensor should carry out surveillance. As an example and not by way oflimitation, strategy 50 may indicate whether the sensor should collectone image or multiple images (such as a series of images) whensurveilling one or more targets.

A status module 36 defines one or more elements of CR 26 that arereadily changeable. Such ready changeability of CR 26 facilitatesdynamic tasking of surveillance resources defined in CR 26. As anexample and not by way of limitation, a status module 36 may provide aswitch for activating and deactivating CR 26. An authorized user 16 maytoggle the switch to activate CR 26 (which may cause one or moresurveillance resources defined in CR 26 to begin surveilling one or moretargets) and deactivate CR 26 (which may cause the surveillanceresources to discontinue the surveillance). As another example, a statusmodule 36 may specify a time interval for surveilling one or moretargets. When the time interval begins, one or more surveillanceresources defined in CR 26 may begin surveilling one or more targets. Atthe end of the time interval, the surveillance resources may discontinuethe surveillance. As another example, a status module 36 may specify atime interval for one or more sensors identified in one or more sensortags 48 in core 34 to surveil one or more targets. When the timeinterval begins, the specified sensors may begin surveilling one or moretargets. At the end of the time interval, the specified sensors maydiscontinue the surveillance. In particular embodiments, one or more XMLor other files include one or more status modules 36. Althoughparticular status modules 36 are illustrated and described, the presentinvention contemplates any suitable status modules 36.

In particular embodiments, ISRR tag 38 identifies an ISRR 52 that is aparent of CR 26 and enables linking between CR 26 and ISRR 52. As anexample and not by way of limitation, CR 26 may be a child of an ISRR 52identified in ISRR tag 38. ISRR 52 may be a parent of multiple CRs 26.ISRR 52 may correspond to a collection problem that multiple CRs 26 mayhelp resolve. As an example and not by way of limitation, ISRR 52 maycorrespond to one or more military threats to Taiwan. CRs 26 that arechildren of ISRR 52 may define surveillance resources for surveillingone or more targets corresponding to the military threats to Taiwan. Inparticular embodiments, one or more XML or other files include one ormore ISRR tags 38. Although a particular ISRR tag 38 is illustrated anddescribed, the present invention contemplates any suitable ISRR tag 38.In particular embodiments, a CR 26 need not be a child of an ISRR 52 andneed not include an ISRR tag 38.

FIG. 4 illustrates example ISRRs 52. In particular embodiments, one ormore XML or other files include one or more ISRRs 52. ISRR 52 a is aparent of ISRRs 52 b and 52 c, and ISRRs 52 b and 52 c are each a parentof one or more CRs 26. As an example and not by way of limitation, ISRR52 a may correspond to a collection problem and ISRRs 52 b and 52 c maycorrespond to subproblems of the collection problem corresponding toISRR 52 a that CRs 26 may help resolve. In particular embodiments, achild of an ISRR 52 inherits one or more attributes from ISRR 52, whichmakes children of ISRR 52 manageable from ISRR 52. In particularembodiments, an ISRR 52 identifies children of ISRR 52 and indicates oneor more relationships among the identified children. As an example andnot by way of limitation, an ISRR 52 may identify a first CR 26, asecond CR 26, and a third CR 26 that are children of ISRR 52. ISRR 52may indicate that first CR 26 has a higher priority than second andthird CRs 26; second CR 26 has a higher priority than third CR 26, but alower priority than first CR 26; and third CR 26 has a lower prioritythan first and second CRs 26. The priorities of first, second, and thirdCRs 26 may change over time automatically or in response to input, whichmay focus different surveillance resources on different constituents ofa collection problem corresponding to ISRR 52 over time. Althoughparticular relationships among particular children of an ISRR 52 aredescribed, the present invention contemplates any suitable relationshipsamong any suitable children of an ISRR 52.

In particular embodiments, a user 16, CTA 18, or both generate a CR 26.As an example and not by way of limitation, a user 16 may want one ormore targets surveilled. User 16 may generate a request for thesurveillance and communicate the request to CTA 18, and the request mayspecify one or more observations for collection on one or more targets.If CTA 18 approves the request, CTA 18 may generate a CR 26 defining oneor more surveillance resources for collecting the specified observationsand communicate CR 26 to collector system 14. CR 26 would include a core34 and may, but need not, include one or more status modules 36. CR 26generated by user 16 may also include an ISRR tag 38, but need notinclude an ISRR tag 38.

FIG. 5 illustrates an example target definition 28. In particularembodiments, target definition 28 does not define a target according totype. Target definition 28 includes a target identifier 54 and alocation identifier 56. Target identifier 54 uniquely identifies targetdefinition 28. In particular embodiments, target identifier 54 is arule-based identifier. In particular embodiments, target identifier 54enables linking between target definition 28 and one or more CRs 26. Asan example and not by way of limitation, a target-CR link 30 between aCR 26 and target definition 28 may specify target identifier 54 tologically link CR 26 to target definition 28. In particular embodiments,a user 16 specifies target identifier 54 to access target definition 28.As an example and not by way of limitation, user 16 may address a pluginto target definition 28 according to target identifier 54 so that theplugin reaches target definition 28. The plugin may modify targetdefinition 28.

Location identifier 56 specifies a geographical location of one or moretargets for surveillance. As an example and not by way of limitation,location identifier 56 may specify one or more sets of latitude andlongitude coordinates identifying a geographical location of one or moretargets for surveillance. As another example, location identifier 56 mayspecify one or more sets of coordinates of a reference grid (such as aDepartment of Defense (DoD) reference grid covering a particulargeographical area) identifying a geographical location of one or moretargets for surveillance. As another example, location identifier mayspecify a vector indicating a location, a direction of movement, and aspeed of movement of one or more targets at a particular time. Sensorsystem 12, collector system 14, or both may use the vector to identify alocation for later surveillance of the one or more targets. A targetdefinition 28 need not always include a location identifier 56. As anexample and not by way of limitation, one or more users 16, CTA 18, orboth may generate a target definition 28 that includes a field for entryof a location identifier 56, but does not include a location identifier56. Later, in response to one or more events, a user 16 may communicatea plugin to target definition 28 supplying a location identifier 56,which may initiate surveillance of one or more targets at a geographicallocation specified in location identifier 56.

In particular embodiments, a user 16, CTA 18, or both generate a targetdefinition 28. As an example and not by way of limitation, a user 16 maywant one or more targets surveilled. User 16 may generate a request forthe surveillance and communicate the request to CTA 18, and the requestmay identify the targets that user 16 wants surveilled. If CTA 18approves the request, CTA 18 may generate one or more target definitions28 defining the one or more identified targets and communicate targetdefinitions 28 to collector system 14. As another example, in responseto one or more recent events, a user 16 may want one or more targetssurveilled immediately. A CR 26 at collector system 14 may define one ormore surveillance resources for surveilling the targets that user 16wants surveilled, and user 16 may have authorization to task thesurveillance resources defined in CR 26 to surveil the targets that user16 wants surveilled. User 16 may generate one or more target definitions28 defining the targets that user 16 wants surveilled and one or moretarget-CR links 30 providing one or more logical links between CR 26 andtarget definitions 28. User 16 may then communicate target definitions28 and target-CR links 30 in one or more plugins to collector system 14.The plugins may facilitate immediate surveillance of the targets thatuser 16 wants surveilled.

One or more users 16, CTA 18, or both direct collector system 14 to tasksurveillance resources. As an example and not by way of limitation, auser 16 may want one or more targets surveilled. User 16 may generate arequest for the surveillance and communicate the request to CTA 18. Therequest may identify the targets that user 16 wants surveilled, specifyone or more observations for collection, or both. User 16 need not havespecialized expertise to generate the request, and relatively simpledescriptions may suffice to identify the targets, specify theobservations for collection, or both. User 16 may communicate therequest to CTA 18, and CTA 18 may review and approve or deny therequest. If CTA 18 approves the request, CTA 18 may generate an envelopeaccording to the request. The envelope would include a core 34 of a CR26 and may, but need not, include one or more status modules 36, may,but need not, include one or more target definitions 28, and may, butneed not, include one or more target-CR links 30. CTA 18 may communicatethe envelope to collector system 14, and collector system 14 may processcontents of the envelope and possibly one or more components atcollector system 14 to generate one or more commands for communicationto one or more sensor systems 12. Components at collector system 14 thatcollector system 14 may process to generate the commands may include oneor more of one or more status modules 36 added to CR 26 after CTA 18communicated the envelope to collector system 14, one or more targetdefinitions 28 at collector system 14 before CTA 18 communicated theenvelope to collector system 14 or added to CR 26 after CTA 18communicated the envelope to collector system 14, and one or moretarget-CR links 30 at collector system 14 before CTA 18 communicated theenvelope to collector system 14 or added to CR 26 after CTA 18communicated the envelope to collector system 14. Collector system 14may communicate the commands to sensor systems 12, which may thenexecute the commands.

As another example, a user 16 may want one or more targets surveilledimmediately. User 16 may generate a plugin for the surveillance andcommunicate the plugin to collector system 14. Because user 16 maycommunicate the plugin directly to collector system 14 without goingthrough CTA 18, the plugin may reduce time requirements otherwiseassociated with tasking surveillance resources. The plugin mayfacilitate immediate surveillance of the targets that user 16 wantssurveilled and may include one or more of the following: one or more newstatus modules 36 facilitating surveillance of the targets user 16 wantssurveilled; one or more instructions to collector system to modify oneor more status modules 36 at collector system 14 to facilitatesurveillance of the targets user 16 wants surveilled; one or moreinstructions to collector system to delete one or more status modules 36at collector system 14 to facilitate surveillance of the targets user 16wants surveilled; one or more new target definitions 28 identifying oneor more of the targets user 16 wants surveilled; one or moreinstructions to collector system 14 to modify one or more targetdefinitions 28 at collector system 14 to facilitate surveillance of thetargets user 16 wants surveilled; one or more instructions to collectorsystem 14 to delete one or more target definitions 28 at collectorsystem 14 to facilitate surveillance of the targets user 16 wantssurveilled; one or more new target-CR links 30 providing one or morelogical links between one or more target definitions 28 and one or moreCRs 26 facilitating surveillance of the targets user 16 wantssurveilled; one or more instructions to collector system 14 to modifyone or more target-CR links 30 at collector system 14 to facilitatesurveillance of the targets user 16 wants surveilled; and one or moreinstructions to collector system 14 to delete one or more target-CRlinks 30 at collector system 14 to facilitate surveillance of thetargets user 16 wants surveilled. User 16 need not have specializedexpertise to generate the plugin, and user 16 may generate the pluginrelatively quickly. The plugin may include one or more XML or otherfiles including one or more relatively simple and relatively intuitivedescriptions of one or more relatively discrete sets of instructions tocollector system 14. Collector system 14 may process contents of theplugin and possibly one or more components at collector system 14 togenerate one or more commands for communication to one or more sensorsystems 12.

FIG. 6 illustrates an example method for dynamically tasking one or moresurveillance resources. The method begins at step 100, where a user 16generates a request for surveillance of one or more targets. At step102, user 16 communicates the request to CTA 18. At step 104, CTA 18reviews the request. At step 106, if CTA 18 denies the request, themethod ends. At step 106, if CTA 18 approves the request, the methodproceeds to step 108, where CTA 18 generates an envelope according tothe request. At step 110, CTA 18 communicates the envelope to collectorsystem 14. At step 112, collector system 14 processes contents of theenvelope. At step 114, collector system 14 generates one or morecommands according to contents of the envelope. At step 116, collectorsystem 14 communicates the commands to one or more sensor systems 12. Atstep 118, sensor systems 12 execute the commands. At step 120, sensorsystems 12 communicate surveillance to collector system 14 resultingfrom execution of the commands. At step 122, collector system 14communicates the surveillance to user 16.

At step 124, in response to one or more events, user 16 generates aplugin. As an example and not by way of limitation, the one or moreevents may include one or more observations made by user 16 fromanalysis of surveillance received at step 122. The plugin may instructcollector system 14 to task one or more of sensor systems 12 to provideimmediate surveillance according to particular needs of user 16. At step126, user 16 communicates the plugin to collector system 14. At step128, collector system 14 processes contents of the plugin. At step 130,collector system 14 generates one or more commands according to contentsof the plugin. At step 132, collector system 14 communicates thecommands to one or more of sensor systems 12. At step 134, one or moreof sensor systems 12 execute the commands. At step 136, sensor systems12 communicate surveillance to collector system 14 resulting fromexecution of the commands. At step 138, collector system 14 communicatesthe surveillance to user 16, at which point the method ends. Althoughparticular steps in the method illustrated in FIG. 6 are illustrated anddescribed as occurring in a particular order, the present inventioncontemplates any suitable steps in the method illustrated in FIG. 6occurring in any suitable order.

Although the present invention has been described with severalembodiments, myriad changes, variations, alterations, transformations,and modifications may be suggested to one skilled in the art, and it isintended that the present invention encompass such changes, variations,alterations, transformations, and modifications as fall within the scopeof the appended claims. The present invention is not intended to belimited, in any way, by any statement in the specification that is notreflected in the claims.

1. A system for dynamically tasking one or more surveillance resources,the system comprising: a first logical layer identifying a collectionrequirement (CR); a second logical layer identifying one or moresurveillance resources in the CR, each of the surveillance resourcescomprising one or more sensors; and a third logical layer specifying howeach of the sensors in the surveillance resources in the CR should carryout surveillance.
 2. The system of claim 1, wherein: the first logicallayer comprises an identifier uniquely identifying the CR; the secondlogical layer comprises one or more sensor tags each identifying one ormore of the sensors; and the third logical layer comprises one or morestrategies that each correspond to one of the sensor tags, each strategyspecifying how the sensors identified in the sensor tag corresponding tothe strategy should carry out surveillance.
 3. The system of claim 1,further comprising a fourth logical layer dynamically tasking one ormore of the surveillance resources in the CR without modifying any ofthe first, second, or third logical layers.
 4. The system of claim 3,wherein the fourth logical layer comprises one or more discrete taskingmodules that each comprise one or more of: one or more status moduleseach defining one or more elements of tasking one or more of thesurveillance resources in the CR; an Intelligence, Surveillance, andReconnaissance Requirement (ISRR) tag identifying an ISRR that is aparent of the CR; one or more target definitions each defining one ormore targets for surveillance according to geography without referenceto target type; and one or more links between the CR and the targetdefinitions, the links logically linking the surveillance resources inthe CR to the targets defined in the target definitions.
 5. The systemof claim 4, wherein the target definitions each comprise one or moresets of latitude and longitude coordinates, one or more sets ofcoordinates of a reference grid, or one or more vectors defining one ormore of the targets.
 6. The system of claim 4, wherein one or more ofthe tasking modules generate in response to one or more events accordingto one or more predetermined criteria.
 7. The system of claim 6, whereinone or more of the events comprise one or more events observed throughsurveillance provided by the surveillance resources in the CR.
 8. Thesystem of claim 4, wherein one or more of the tasking modules modify inresponse to one or more events according to one or more predeterminedcriteria.
 9. The system of claim 8, wherein one or more of the eventscomprise one or more events observed through surveillance provided bythe surveillance resources in the CR.
 10. The system of claim 1, whereinone or more sensor systems each comprise one or more of the sensors, oneor more of the sensor systems each comprising one or more of one or moreunmanned satellites and one or more unmanned aerial vehicles (UAVs). 11.The system of claim 1, wherein surveillance comprises collecting one ormore images of one or more targets.
 12. A method for dynamically taskingone or more surveillance resources, the method comprising: using a firstlogical layer, identifying a collection requirement (CR); using a secondlogical layer, identifying one or more surveillance resources in the CR,each of the surveillance resources comprising one or more sensors; andusing a third logical layer, specifying how each of the sensors in thesurveillance resources in the CR should carry out surveillance.
 13. Themethod of claim 12, wherein: the first logical layer comprises anidentifier uniquely identifying the CR; the second logical layercomprises one or more sensor tags each identifying one or more of thesensors; and the third logical layer comprises one or more strategiesthat each correspond to one of the sensor tags, each strategy specifyinghow the sensors identified in the sensor tag corresponding to thestrategy should carry out surveillance.
 14. The method of claim 12,further comprising, using a fourth logical layer, dynamically taskingone or more of the surveillance resources in the CR without modifyingany of the first, second, or third logical layers.
 15. The method ofclaim 14, wherein the fourth logical layer comprises one or morediscrete tasking modules that each comprise one or more of: one or morestatus modules each defining one or more elements of tasking one or moreof the surveillance resources in the CR; an Intelligence, Surveillance,and Reconnaissance Requirement (ISRR) tag identifying an ISRR that is aparent of the CR; one or more target definitions each defining one ormore targets for surveillance according to geography without referenceto target type; and one or more links between the CR and the targetdefinitions, the links logically linking the surveillance resources inthe CR to the targets defined in the target definitions.
 16. The methodof claim 15, wherein the target definitions each comprise one or moresets of latitude and longitude coordinates, one or more sets ofcoordinates of a reference grid, or one or more vectors defining one ormore of the targets.
 17. The method of claim 15, wherein one or more ofthe tasking modules generate in response to one or more events accordingto one or more predetermined criteria.
 18. The method of claim 17,wherein one or more of the events comprise one or more events observedthrough surveillance provided by the surveillance resources in the CR.19. The method of claim 15, wherein one or more of the tasking modulesmodify in response to one or more events according to one or morepredetermined criteria.
 20. The method of claim 19, wherein one or moreof the events comprise one or more events observed through surveillanceprovided by the surveillance resources in the CR.
 21. The method ofclaim 12, wherein one or more sensor systems each comprise one or moreof the sensors, one or more of the sensor systems each comprising one ormore of one or more unmanned satellites and one or more unmanned aerialvehicles (UAVs).
 22. The method of claim 12, wherein surveillancecomprises collecting one or more images of one or more targets.
 23. Asystem for dynamically tasking one or more surveillance resources, thesystem comprising: means for identifying a collection requirement (CR);means for identifying one or more surveillance resources in the CR, eachof the surveillance resources comprising one or more sensors; and meansfor specifying how each of the sensors in the surveillance resources inthe CR should carry out surveillance.